Skip to content

docs: add deprecation banners to Android v6 and the legacy sourcemaps tool - #33

Merged
krassx merged 1 commit into
mainfrom
docs/legacy-deprecation-banners
Sep 2, 2026
Merged

docs: add deprecation banners to Android v6 and the legacy sourcemaps tool#33
krassx merged 1 commit into
mainfrom
docs/legacy-deprecation-banners

Conversation

@krassx

@krassx krassx commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Replaces #29. #29 shows as "merged", but it merged into docs/flutter-network-layering — a stacked parent branch, not main — so none of its content ever reached main. This PR carries the same commit, based directly on main. See the note at the bottom.

Two sections of the site are superseded, and neither says so on the page.

Android SDK 6.x — 21 pages

Today the only signal that v6 is the previous major version is its placement under "Previous versions" in the sidebar. That is invisible to anyone arriving from a search result, an old bookmark, or a shared link — which is most of the traffic these pages get.

:::caution[Previous version]
This page documents Bugsee Android SDK **6.x**, the previous major version. The current
line is **7.x** — see [Migrating from 6.x to 7.x](/sdk/android/migration) to upgrade, or
[Installation](/sdk/android/installation) to start a new integration.
:::

Given the migration guide describes 7.x as a near-total rewrite, silently following a v6 page is a costly wrong turn.

tools/sourcemaps.md — 1 page

/cli/sourcemaps/ already calls this page's subject "the older bugsee-sourcemaps npm tool", superseded by the CLI's debug-ID-based flow. The page itself said nothing. The banner reuses the CLI page's own wording rather than inventing new framing.

Approach

Modelled on sdk/xamarin/installation.mdx, the pattern the site already uses for superseded content. Banners sit after any MDX import statements, matching that file's placement. All 21 v6 pages carry exactly one banner; front matter untouched.

Conflict resolution carried forward

sdk/android/v6/feedback.mdx needed a merge with the already-merged #27, which fixed the built in single threaded typo in the same region this banner occupies. Kept both — banner on top, corrected sentence below. Verified after the cherry-pick: built in single threaded → 0, built-in single-threaded → 1.

Why this PR exists

The four PRs were stacked (#31#30#29#28). Deleting each head branch after merging closed the child PR one second later, because GitHub closes a PR when its base branch is deleted — and #29 merged into its stacked parent rather than into main. Only #31 actually landed. This PR and #32/#33 are flat and independent, so the failure mode cannot recur.

Checks

npx cspell 288 files / 0 issues · npm run build succeeds, no broken links

🤖 Generated with Claude Code

… tool

Both sections are superseded, and neither says so on the page itself.

Android SDK 6.x (21 pages)
  The only signal that v6 is the previous major version is its position
  under "Previous versions" in the sidebar — invisible to anyone
  arriving from a search result, an old bookmark, or a shared link. Adds
  a :::caution banner to every v6 page pointing at the 6.x -> 7.x
  migration guide and at the current installation page. Modelled on the
  Xamarin SDK's per-page deprecation banner, which is the pattern the
  rest of the site already uses for superseded content.

tools/sourcemaps.md
  /cli/sourcemaps/ already describes this page's subject as "the older
  bugsee-sourcemaps npm tool", superseded by the CLI's debug-ID-based
  flow — but the page itself carried no such notice, so a reader landing
  on it directly had no way to know it is not the recommended path.
  Adds a banner using the CLI page's own wording.

Banners are placed after any MDX import statements, matching the
placement in sdk/xamarin/installation.mdx.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Change-Id: I3dc9b52b046c8f1b7a5e1c87ea5f252eb288b71e
@krassx
krassx merged commit c05ff03 into main Sep 2, 2026
1 check passed
@krassx
krassx deleted the docs/legacy-deprecation-banners branch September 2, 2026 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant